Skip to content

todoist 0.1.0: a read-only drive app hosting the Todoist lens - #273

Merged
michielbdejong merged 2 commits into
mainfrom
claude/todoist-app
Oct 2, 2026
Merged

michielbdejong merged 2 commits into
mainfrom
claude/todoist-app

Conversation

@michielbdejong

Copy link
Copy Markdown
Contributor

Refs #99, #46.

Gives integrations/issue-tracker/todoist.ts a host: the Todoist drive app in integrations/issue-tracker/todoist-app/ (catalog id todoist, mapped in apps.mjs APP_FOLDERS).

  • Connect and import: it connects through the host's consent bar and imports the account's active tasks into rows of the shared class issue-v1. It adopts that class on first open, like the GitHub issues app. Shared fields go through ontology-kit's resolver; the Todoist id, presence, last-seen, priority, project and source are row-extras.
  • Todoist: define completion and disappearance behavior for active-task imports #99's disappearance behaviour, as todoist.ts defines it:
    • a task missing from a complete read is looked up by id once and marked completed, deleted, unavailable or unconfirmed;
    • only completed closes it;
    • a partial read settles nothing;
    • no row is removed, and nothing is sent to Todoist.
  • Unchanged refresh: a refresh that finds nothing changed writes no row. last-seen stays off active rows, and the App records the read's time once.
  • Fixture: fixtures/todoist/ serves synthetic data (synthetic.mjs, hand-written from Todoist's API v1 docs, invented) until issue-tracker: record a todoist mock-proxy fixture #46 records api/. It has drivers for completing, deleting and hiding tasks and for failing requests, and is registered with the mock proxy.
  • E2E: e2e/todoist.spec.ts in the issue-tracker lane covers catalog install, connect, 5 issue-v1 rows, and a reload with byte-identical rows. A task completed in Todoist turns up done; one made unreachable stays open as unavailable.
  • Catalog: devonian-todoist becomes the app entry todoist (0.1.0, apps/todoist/0.1.0/ui.js, 25,926 bytes, limit 28,600), still enabled: false. The LocalThought-flow fields are dropped, as moneybird 0.1.0: publish the drive app, install it from the catalog (#102) #242 did for Moneybird.

Checks (local, pin a12b74a): issue-tracker unit (248 passed, 4 skipped) and e2e (2 passed). Also: tooling tests 251/251, apps and ontology checks, certify, e2e tsc, oxlint (0 errors) and oxfmt.

Not verified: anything against a live Todoist account (#46). In particular, the fixture assumes GET /tasks/{id} returns a completed task with checked: true rather than 404; the README says what happens otherwise.

🤖 Generated with Claude Code

Refs #99, #46.

Give integrations/issue-tracker/todoist.ts a host: a drive app in
integrations/issue-tracker/todoist-app/ (apps.mjs APP_FOLDERS maps the
catalog id `todoist` there) that connects through store.proxy.connect,
reads the active tasks and projects through the host's proxy client, and
imports them into rows of the shared class issue-v1, adopting the class on
first open like the GitHub issues app (renders, row-extras, classtype).
Shared fields go through ontology-kit's resolver; the Todoist task id,
presence, last-seen, priority, project and source are row extras.

The pass runs #99's disappearance behaviour as todoist.ts defines it: a
task missing from a complete read is looked up by id once and marked
completed, deleted, unavailable or unconfirmed; only completed closes it, a
partial read settles nothing, no row is removed, nothing is sent to
Todoist. A refresh that finds nothing changed writes no row: last-seen is
kept off active rows (the App records the read's time once).

The mock-proxy fixture in fixtures/todoist/ now serves SYNTHETIC rows
(synthetic.mjs, hand-written from Todoist's API v1 documentation, invented
data) until #46 records api/, with drivers (completeTask, reopenTask,
deleteTask, removeTask, failNext, snapshot); it is registered with the mock
proxy. The issue-tracker lane gains e2e/todoist.spec.ts: catalog install,
connect, five issue-v1 rows, a reload that leaves every row byte-for-byte,
a task completed in Todoist that turns up done, one made unreachable that
stays open as unavailable.

Catalog: `devonian-todoist` becomes the app entry `todoist` (0.1.0,
apps/todoist/0.1.0/ui.js, 25,926 bytes; enabled: false).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
# Conflicts:
#	integrations/READINESS.md
#	integrations/issue-tracker/README.md
@michielbdejong
michielbdejong merged commit 7fb110f into main Oct 2, 2026
33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant